Skip to content

Updated failsafe to use same number as ;afk#2239

Merged
rpherbig merged 1 commit intocombat-trainer-health-thresholdfrom
unknown repository
Feb 11, 2018
Merged

Updated failsafe to use same number as ;afk#2239
rpherbig merged 1 commit intocombat-trainer-health-thresholdfrom
unknown repository

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented Dec 18, 2017

No description provided.

Comment thread combat-trainer.lic
def execute(game_state)
custom_require.call('tendme') if bleeding? && !Script.running?('tendme')
fput 'exit' if health < 40
fput 'exit' if health < get_settings.health_threshold
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not as simple as using get_settings here because then it won't be using the same settings as the rest of combat-trainer (i.e. the script could have been executed with args). You'll want to pass the right settings into SafetyProcess (see line 2154).

@ghost
Copy link
Copy Markdown
Author

ghost commented Dec 18, 2017 via email

@rpherbig
Copy link
Copy Markdown
Contributor

We don't really know if people do or not. I could see someone wanting to change the threshold for a safer or riskier hunt.

@Sarvatt
Copy link
Copy Markdown
Contributor

Sarvatt commented Feb 11, 2018

Can we push this and make an issue to extend it so it works in every yaml? This would be a great feature to have and it has been asked for.

@rpherbig rpherbig changed the base branch from master to combat-trainer-health-threshold February 11, 2018 15:30
@rpherbig rpherbig merged commit ecd647c into elanthia-online:combat-trainer-health-threshold Feb 11, 2018
rpherbig added a commit that referenced this pull request Feb 12, 2018
* Updated failsafe to use same number as ;afk (#2239)

* Use local settings to determine health_threshold
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants